[TASK-396857] [Apps] Group Perfect Meetings databases for demo cleanup - #132

Description

Attribution

• Custom agent: Neil 3000
• Custom agent created by: Neil Sarkar (nsarkar@makenotion.com)
• Custom agent requested by: Neil Sarkar (nsarkar@makenotion.com)
• Triggered from Slack thread: View thread
• Notion thread: View thread

[written by Neil 3000]

New Perfect Meetings installations create their four databases under Perfect Meetings Resources, linked from the app home. This gives demos a single data-cleanup page while keeping existing resource IDs stable. Existing installations need a manual database move; the custom agent and Worker remain separate, so this is not full uninstall.

Task: Group Perfect Meetings template resources under one cleanup page

The resources page has no explanatory text, only the four child database links. Omitting those links fails SDK provisioning because each child database must appear exactly once in its parent page. README cleanup guidance and the catalog copy change have been removed.

Resource declaration

This declaration was exercised in the successful local deployment:

const resources = page({
  resourceId: "perfect-meetings-resources",
  properties: { title: notion.text("Perfect Meetings Resources") },
  content: `<database url="meetings-db" inline="false">Meetings</database>

<database url="people-db" inline="false">People</database>

<database url="companies-db" inline="false">Companies</database>

<database url="sync-runs-db" inline="false">Workflow runs</database>`,
})

Testing

• App checks, all 168 existing unit tests, and build passed on Node 26. Catalog validation, generated agent-file checks, targeted Markdown/format checks, and commit hooks passed.
• Deployed the revised template to an isolated local Notion workspace. The real client shows only Meetings, People, Companies, and Workflow runs under Perfect Meetings Resources. Fresh server reads confirm these are the page's only four child blocks and each database has that page as its parent.
• The stock smoke fixture was adapted temporarily for current NaC imports and CLI arguments, with workspace deletion disabled. Deployment completed successfully. Destructive cleanup, workflow execution, and existing-install migration were not exercised.

Agent QA proof (after-only)